Alert systems and methods for a vehicle

ABSTRACT

A method of alerting a driver of a vehicle is provided. The method includes: receiving conditions data from one or more collision avoidance systems; determining an alert mode based on the conditions data; receiving a fault status indicating a fault of at least one of a haptic alert device, a visual alert device, and an auditory alert device; resetting the alert mode to an override mode based on the fault status; and selectively generating an alert pattern for at least one of a haptic alert device, a visual alert device, and an auditory alert device that does not have a fault based on the override mode of the alert mode.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.61/663,516, filed Jun. 22, 2012 which is incorporated herein byreference in its entirety.

TECHNICAL FIELD

The technical field generally relates to driver alert systems andmethods, and more particularly relates to control methods and systemsfor driver alert systems of a vehicle.

BACKGROUND

Collision avoidance systems warn drivers of potential collision threatsthat may be in the line-of-sight of the driver (e.g., detected byon-board vehicle sensors) or out of the line-of-sight of the driver(e.g., determined from wireless vehicle-to-vehicle communications and/orvehicle-to-infrastructure communications). Collision avoidance systemsmay generate visual, auditory, or haptic alerts to warn a vehicle driverof the potential collision threats. Typically, the collision avoidancesystems are implemented as separate systems. Thus, alerts may begenerated by some collision avoidance systems without regard to alertsthat are generated by other collision avoidance systems. If more thanone alert is generated to the vehicle driver at any one time, themultiple alerts might have the potential to distract the driver fromavoiding the collision.

Accordingly, it is desirable to provide methods and systems forcoordinating the alerting of the driver of the vehicle using anycombination of the auditory, visual, and haptic alerts. Furthermore,other desirable features and characteristics of the present inventionwill become apparent from the subsequent detailed description and theappended claims, taken in conjunction with the accompanying drawings andthe foregoing technical field and background.

SUMMARY

A method of alerting a driver of a vehicle is provided. In oneembodiment, the method includes: receiving conditions data from one ormore collision avoidance systems; determining an alert mode based on theconditions data; receiving a fault status indicating a fault of at leastone of a haptic alert device, a visual alert device, and an auditoryalert device; resetting the alert mode to an override mode based on thefault status; and selectively generating an alert pattern for at leastone of a haptic alert device, a visual alert device, and an auditoryalert device that does not have a fault based on the override mode ofthe alert mode.

A control system is provided for alerting a driver of a vehicle. In oneembodiment, the system includes a first module that receives conditionsdata from one or more collision avoidance systems, that determines analert mode based on the conditions data, that receives a fault statusindicating a fault of at least one of a haptic alert device, a visualalert device, and an auditory alert device, and that resets the alertmode to an override mode based on the fault status. A second moduleselectively generates an alert pattern for at least one of a hapticalert device, a visual alert device, and an auditory alert device thatdoes not have a fault based on the override mode of the alert mode.

DESCRIPTION OF THE DRAWINGS

The exemplary embodiments will hereinafter be described in conjunctionwith the following drawing figures, wherein like numerals denote likeelements, and wherein:

FIG. 1 is a functional block diagram illustrating a vehicle thatincludes a driver alert system in accordance with exemplary embodiments;

FIG. 2 is a dataflow diagram illustrating an alert control system of thedriver alert system in accordance with exemplary embodiments; and

FIGS. 3-8 are flowcharts illustrating alert methods that may beperformed by the alert systems in accordance with exemplary embodiments.

DETAILED DESCRIPTION

The following detailed description is merely exemplary in nature and isnot intended to limit the application and uses. Furthermore, there is nointention to be bound by any expressed or implied theory presented inthe preceding technical field, background, brief summary or thefollowing detailed description. It should be understood that throughoutthe drawings, corresponding reference numerals indicate like orcorresponding parts and features. As used herein, the term module refersto an application specific integrated circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group) and memory thatexecutes one or more software or firmware programs, a combinationallogic circuit, and/or other suitable components that provide thedescribed functionality.

Referring now to FIG. 1, a vehicle 10 is shown having a driver alertsystem 12 in accordance with various embodiments. The driver alertsystem 12 is associated with one or more collision avoidance systems 14,16 of the vehicle 10. The driver alert system 12 generally alerts adriver of one or more conditions that are detected and indicated by thecollision avoidance system(s) 14, 16 in accordance with variousembodiments. Although the figures shown herein depict examplearrangements of elements, additional intervening elements, devices,features, or components may be present in actual embodiments. It shouldalso be understood that FIG. 1 is merely illustrative and may not bedrawn to scale.

As shown, the vehicle 10 includes one or more line-of-sight collisionavoidance or mitigation systems 14, and one or more non-line-of-sightcollision avoidance or mitigation systems 16. The line-of-sightcollision avoidance systems 14 generally include one or more on-boardvehicle sensors (not shown) (e.g., camera, radar, and/or lidar)communicatively coupled to a control module (not shown) that detect apotential for a collision based on the vehicle sensor signals. Exemplaryline-of-sight collision avoidance systems 14 include, but are notlimited to, lane departure warning or lanekeeping assist systems 18,front park assist systems 20, rear park assist systems 22, front andrear automatic braking systems 24, rear cross traffic alert systems 26,adaptive cruise control (ACC) systems 28, side blind zone (or spot)detection systems 30, lane change alert systems 32, driver attention(e.g., distraction- and/or drowsiness-monitoring) systems 34, and frontand rear pedestrian detection systems 36.

The non-line-of-sight collision avoidance systems 16 generally includeone or more communication systems or devices (not shown) that candetermine or forecast a potential collision. Exemplary non-line-of-sightcollision avoidance systems include, but are not limited to, vehiclecommunication systems that communicate between the vehicle 10 and othervehicles (not shown) (e.g., vehicle-to-vehicle communication systems38), vehicle communication systems that communicate between the vehicle10 and an infrastructure (not shown) (e.g., vehicle-to-infrastructurecommunication systems 40) and vehicle communication systems thatcommunicate between the vehicle 10 and an pedestrians/cyclists (e.g.,vehicle-to-pedestrian communication systems 41) to forecast potentialcollisions due to traffic. As can be appreciated, in variousembodiments, any one of the line-of-sight collision avoidance systems 14or the non-line-of sight collision avoidance systems 16 can include bothvehicle sensors and communication systems to detect activity eitherinside the line-of-sight of the driver or outside of the line-of-sightof the driver.

A control module 42 receives signals 44, 46 from the various collisionavoidance systems 14, 16 indicating one or more potential collisionconditions. As can be appreciated, in various other embodiments, thecontrol module 42 may be integrated with other control modules (notshown) of the vehicle 10, and/or may be implemented separately for eachcollision avoidance system 14, 16. The control module 42 may also be aplug-in device that is installed into an onboard diagnostics connectorof the vehicle (OBD-II), a retrofit module that is collocated with anexisting vehicle module (i.e., installed at the host module using anadaptation connector), or as a replacement part for an existing vehiclesystem (i.e., inside rear-view mirror assembly). The control module 42may also be a wireless device that is communicatively couples to thevehicle 10 over a short range wireless connection such as Wi-Fi,Bluetooth, NFC or similar.

The control module 42 generates control signals 48 to alert devicesand/or control devices 50 such that a driver can be alerted of thecondition and/or such that vehicle functions can be performed tominimize or prevent the collision. In various embodiments, the alertdevices can include, one or more haptic alert devices 50 (e.g., one ormore haptic alert devices of a vehicle seat assembly described, one ormore haptic alert devices of a steering wheel assembly, etc.), one ormore auditory alert devices 52 (e.g., warning chimes or beeps, etc.),one or more visual alert devices 54 (e.g., warning lamps, an informationcenter, a screen of an infotainment system, LED panel, head-up display,display reflected off windshield, etc.), and auditory, visual, andhaptic devices of an infotainment system 56. The control devices caninclude, but are not limited to, a vehicle system control device 58 thatperforms vehicle braking, vehicle system control device 58 that adjuststhe torque or position of the vehicle steering, or other drivingmaneuvers. In various embodiments, the control module 42 coordinates thegeneration of the control signals 48 such that the alerts alert thedriver in a way that does not distract the driver from avoiding thecollision.

Referring now to FIG. 2 and with continued reference to FIG. 1, adataflow diagram illustrates various embodiments of an alert controlsystem that may be embedded within the control module 42. Variousembodiments of alert control systems according to the present disclosuremay include any number of sub-modules embedded within the control module42. As can be appreciated, the sub-modules shown in FIG. 2 may becombined and/or further partitioned to similarly coordinate and providedriver alerts and/or request vehicle functions to be performed.

In various embodiments, inputs to the alert system may be sensed fromthe vehicle 10, received from other control modules (not shown) withinthe vehicle 10 (e.g., through a vehicle communication bus or anintra-vehicle wireless communication), received from modules remote fromthe vehicle 10 (e.g., through inter-wireless communication or cellularcommunication), received from one or more sensors (not shown) of thevehicle 10, and/or determined/modeled by other sub-modules (not shown)within the control module 42. In various embodiments, the control module42 includes an alert settings datastore 70, a user configuration module72, a monitoring module 74, a mode determination module 76, and apattern determination module 78. In various embodiments, the alertsettings datastore 70 may reside in a local vehicle module, in a plug-invehicle accessory device, in user-removable storage (e.g., USB flashdrive, Secure Digital SD, etc.), in the storage of a user accommodateddevice (e.g., consumer smartphone or key fob that is wirelessly pairedto the vehicle 10), or in a cloud database. For exemplary purposes, thealert settings datastore 70 is described as being a part of the controlmodule 42.

The alert settings datastore 70 stores predefined alert settings and/oruser configured alert settings, as will be discussed in more detailbelow. As can be appreciated, the alert settings datastore 70 caninclude volatile memory that temporarily stores the settings,non-volatile memory that stores the settings across key cycles, or acombination of volatile and non-volatile memory.

The user configuration module 72 manages the display of a configurationmenu 80, and manages user input 82 received from a user interacting withthe configuration menu 80. As can be appreciated, the configuration menu80 can be displayed on a display device within the vehicle 10 (e.g., viaan information center), can be displayed on a display device that isremote from the vehicle 10 (e.g., a computing device or personalhandheld device), or can be displayed on a device connected to thevehicle 10 (e.g., a technician tool).

In various embodiments, the configuration menu 80 may be implemented asa main menu with one or more sub-menus. Each menu or sub-menu includesselectable options that, when selected, allow a user to configurevarious alert settings associated with the haptic alert devices 50, theauditory alert devices 52, the visual alert devices 54, and/or theinfotainment system 56. The alert settings for the haptic alert devices50 can include, but are not limited to, an occurrence of the vibration(e.g., whether or not to perform the vibration for a particular mode), alocation of the vibration (e.g., at a particular location on seat orother haptic device), an intensity of the vibration, a duration of thevibration, a rate of the vibration, and/or a frequency of the pulses ofthe vibration. The alert settings for the auditory alert devices 52 caninclude, but are not limited to, an occurrence of the auditory alert(e.g., whether or not to perform the auditory alert), a sound level ofthe auditory alert, a sound type of the auditory alert (e.g., aparticular narrow-band chime or broadband auditory warning signal), aduration of the auditory alert, a rate of the auditory alert, and/or afrequency of sounds of the auditory alert. The alert settings for thevisual alert devices 54 can include, but are not limited to, anoccurrence of the visual alert (e.g., whether or not to perform thevisual alert), a location of the visual alert (e.g., whether on a headsup display, an LED panel, or other visual alert device), a visual typeof the visual alert (e.g., a particular color or symbol), a duration ofthe visual alert, a rate of the visual alert, and/or a frequency ofvisuals of the visual alert.

The alert settings for the infotainment system 56 can include, but arenot limited to, an occurrence of an auditory muting, haptic feedback, orpattern display (e.g., whether or not to perform the auditory muting,the haptic feedback, and/or pattern display for a particular mode), anda type of auditory muting, haptic feedback, or pattern display thatshould be applied. For example, a rapid pulsing pattern may betransmitted via the finger making contact with a touch screen when acollision may be imminent. In another example, the radio can beintelligently muted based on interior vehicle conditions indicating avolume level of the infotainment system 56.

In various embodiments, the configuration menu 80 allows the alertsettings to be configured for alert types such as individual alertconditions, certain types or groups of alert conditions, particulardriving scenarios, and/or for particular vehicle conditions. Theindividual alert conditions can include, but are not limited to,conditions associated with the various collision avoidance systems. Theparticular driving scenarios can include, but are not limited to,vehicle occupancy type conditions (e.g., as determined based on seatbeltsignals, or seat compression signals, number of consumer devicepairings, number of consumer devices discovered, rear seat entertainmentsystem usage, passenger door opening/closing inferences, etc.), ambientconditions (such as day or night, or weather conditions, which forexample, can be derived from wiper usage and outside air temperature),driver self-rated attention, distraction, or drowsy state (e.g., high,medium, or low), and a type of road that the vehicle is traveling onbased on a digital map information (e.g., unique settings may beconfigured for different types of road classes: residential, arterial,highway, limited access, etc.). As can be appreciated, other mapattributes such as posted speed limits may also be used (e.g., specificsettings may apply based on the current posted speed limit). The digitalmap database may reside inside an embedded vehicle module, on a customerdevice, or on a remote server (which may be accessed in real time oraccessed as a downloaded datastore). The vehicle conditions can include,but are not limited to, when the vehicle is experiencing a severe systemmalfunction (e.g., a specific device trouble code has activated or thedriver has engaged the vehicle hazard lights).

The type or groups of alert conditions may include a grouping or type ofany of the alert conditions, driving scenarios, and vehicle conditionsand can include, but are not limited to, parking type conditions versusdriving type (non-parking) conditions, and various collision threatconditions (e.g., minor threats verses imminent threats, and variousthreat levels there between). In various embodiments, alert conditionsmay also be configured to be specific to an identity of the currentdriver (e.g., the identity can be determined based on a current keyfobor driver memory seat selection, or driver identity based on aprioritized paired device).

Based on the user input 82 received from the user interacting with theconfiguration menu 80 (e.g., via one or more user input devices), theuser configuration module 72 stores the user configured alert settings84 in the alert settings datastore 70. For example, as shown in theexemplary flowcharts of FIGS. 3 and 4 and with continued reference toFIG. 2, a driver selection menu is displayed requesting selection of aparticular driver at 300. If a driver selection is not received at 310,it is determined with the user input 82 indicates to exit the driverselection menu at 305. If the user input 82 indicates to exit the driverselection menu at 305, the driver selection menu is exited and themethod may end at 308.

If, however, the user input does not indicate to exit the driverselection menu at 305, the driver selection menu is displayed at 300.Upon receipt of user input 82 indicating a driver selection at 310, analert type selection menu is displayed requesting selection of aparticular alert type at 320. For example, the alert type may be analert condition type, a group of alert conditions type, a drivingscenario type, or a vehicle condition type.

If the user input 82 indicates that an alert condition type is selectedat 330, an alert condition selection menu is displayed requestingselection of a particular alert condition at 340. Upon receipt of userinput 82 indicating a selection of a particular alert condition at 350,the particular alert condition is temporarily stored at 360. Thereafter,the method continues at 365.

If, at 370, the user input 82 indicates that a group of alert conditionstype is selected, a group of alert conditions selection menu isdisplayed requesting selection of a particular group or type of alertconditions at 380. Upon receipt of user input 82 indicating a selectionof a particular group or type of alert conditions at 390, the particulargroup or type of alert conditions is temporarily stored at 400.Thereafter, the method continues at 365.

If, at 410, the user input 82 indicates that a driving scenario type isselected, a driving scenarios selection menu is displayed requestingselection of a particular driving scenario at 420. Upon receipt of userinput 82 indicating a selection of a particular driving scenario at 430,the particular driving scenario is temporarily stored at 440.Thereafter, the method continues at 365.

If, at 450, the user input 82 indicates that a vehicle conditions typeis selected, a vehicle conditions selection menu is displayed requestingselection of a particular vehicle condition at 460. Upon receipt of userinput 82 indicating a selection of a particular vehicle condition at470, the particular vehicle condition is temporarily stored at 480.Thereafter, the method continues at 365.

If, at 490, the user input 82 indicates to exit the alert type selectionmenu, the driver selection menu is displayed at 300. Otherwise, thealert type selection menu is displayed at 320.

After 365 (in FIG. 4), an alert device selection menu is displayedrequesting selection of a particular alert device (e.g., a hapticdevice, an auditory device, a visual device, an infotainment system,etc.) at 500. Upon receipt of user input 82 indicating a selection of aparticular alert device at 510, an alert settings selection menu isdisplayed requesting selection of a particular alert setting at 520.Upon receipt of user input 82 indicating a selection of a particularalert setting at 530, the particular alert setting is associated withthe temporarily stored alert type at 540.

If, at 550, the user input 82 indicates to exit the alert settingsselection menu, the alert device selection menu is displayed at 500.Otherwise, the alert settings selection menu is displayed at 520. If at510, the user input 82 does not indicate an alert type and the userinput 82 does not indicate to exit the alert device menu at 560, thealert device selection menu is displayed at 500. If, however, the userinput 82 does not indicate an alert type at 510 rather, the user inputindicates to exit the alert device selection menu at 560, the methodreturns to 320 to display the alert type selection menu at 570. As canbe appreciated, the method may iterate until the user has completedconfiguration of the selected alert settings and has exited the driverselection menu.

With reference back to FIG. 2, the monitoring module 74 monitors inputdata 86 associated with the alert devices 50-56 to determine whether thealert devices 50-56 are operating properly. If the monitoring module 74determines that one or more of the alert devices 50-56 is not operatingproperly (i.e., malfunctioning), the monitoring module 74 generates awarning message 88, generates a warning signal 90, and/or generates afault condition status 92 that can be evaluated by the modedetermination module 76. The fault condition status 92 may indicate atype of fault and the particular faulty device.

In various embodiments, the warning message 88 may include a diagnosticcode that indicates a fault of the alert device 50-56. The warningmessage 88 may be communicated to an occupant of the vehicle 10 (e.g.,via an information center of the vehicle 10), may be communicated to aremote location (e.g., via a telematics system of the vehicle 10), maybe communicated to an accommodated or plug-in device, and/or may beretrieved by a technician (e.g., via a technician tool thatcommunicatively couples to a communication bus of the vehicle 10). Invarious embodiments, the warning signal 90 is a control signal thatactivates an alert device 50-56 other than the device that contains thefault. For example, the warning signal 90 can be a visual alert device54 of the vehicle 10, can be a control signal that activates an auditoryalert device 52 of the vehicle 10, and/or can be a control signal thatactivates a haptic alert device 50.

The mode determination module 76 determines a current alert mode 94based on various vehicle conditions indicated by the signals 44, 46. Thevehicle conditions are conditions that may require an alert to thedriver and can be received from the various line-of-sight collisionavoidance systems 14 (FIG. 1) as collision avoidance system conditionsdata 96, can be received from the non-line-of-sight collision avoidancesystems 16 as vehicle-to-vehicle conditions data 98, and/or asvehicle-to-infrastructure conditions data 100 and/orvehicle-to-pedestrian conditions data 41. Based on the conditions data96-100, the mode determination module 76 sets the alert mode 94 toindicate one or more alert conditions, one or more vehicle conditions,and/or one or more driving scenarios. In various embodiments, the modedetermination module 76 may set the alert mode 94 (e.g., to an overridemode) based on a determination of an imminent collision threat indicatedby one of the systems 14, 16 (FIG. 1).

In various embodiments, the mode determination module 76 may determinethat the conditions data 96-100 present multiple alert modes 94. In sucha case, the mode determination module 76 generates the multiple alertmodes or, alternatively, arbitrates between the alert modes based on apriority scheme to generate a single alert mode 94, or alternatively,arbitrates between the alert modes to create a combined alert. Invarious embodiments, the mode determination module 76 monitors the faultcondition status 92 of the alert devices. 50-56 (FIG. 1). The modedetermination module 76 sets the alert mode 94 based on the faultcondition status 92. For example, if the fault condition status 92indicates a fault of the haptic device 50 (FIG. 1), the modedetermination module 76 may set the alert mode 94 to an override mode.

For example, as shown in the flowchart of FIG. 5 and with continuedreference to FIG. 2, the conditions data 96-100 is received at 600. Theconditions data 96-100 is evaluated at 610 and the alert mode 94 (ormodes) is determined at 620. Based on the evaluation, the alert mode 94can indicate one or more alert conditions, one or more drivingscenarios, and/or one or more vehicle conditions.

It is determined whether a fault condition status 92 has been receivedat 630. If a fault condition status 92 has not been received at 630, orthe fault condition status 92 indicates that the fault is not a fault ofan alert device 50-56 (FIG. 1) that is associated with the alert mode94, the method may end at 660. If, however, a fault condition status 92is received at 630, and the fault condition status 92 indicates a faultof an alert device 50-56 (FIG. 1) associated with the alert mode 94 at640, the alert mode 94 is set to an override mode based on the faultydevice at 650. Thereafter, the method may end at 660.

With reference back to FIG. 2, the pattern determination module 78determines one or more alert patterns based on the alert mode 94. Thealert patterns include haptic alert patterns 104, visual alert patterns106, and/or auditory alert patterns 108 that are used by the hapticalert devices 50 (FIG. 1), the visual alert devices 54 (FIG. 1), theauditory alert devices 52 (FIG. 1), and/or the infotainment system 56(FIG. 1) to generate the alerts. Depending on the type of pattern (e.g.,haptic, visual, and/or audio), the patterns may indicate a location orlocations of the alert within the alert device 50-56 (e.g., a vibrationat a particular location or locations on seat or other haptic device),an auditory type of the alert (e.g., a particular chime), a visual typeof the alert (e.g., a particular color or symbol) an intensity of thealert, a duration of the alert, a rate of the alert and/or a frequencyof vibration pulses, visuals, or sounds of the alert.

In various embodiments, the pattern determination module 78 determinesthe alert patterns 104-108 for a particular device by retrievingpredefined alert settings 110, and/or the user configured alert settings84 from the alert settings datastore 70. The alert settings 84, 110 areretrieved based on the alert mode 94. For example, as shown in theflowchart of FIG. 6 and with continued reference to FIG. 2, one or morealert modes 94 are received (for ease of the discussion the method willbe discussed in the context of a single alert mode 94) at 700.

If the alert mode 94 is an override mode at 710, predefined alertsettings 110 associated with the particular override mode are retrievedfrom the alert settings datastore 70 at 720 and one or more of the alertpatterns 104-108 are set based on the predefined alert settings 110 at730. Thereafter, the method may end at 735.

If, however, the alert mode 94 is not an override mode at 710, and userconfigured alert settings 84 exist for all of the one or more alertconditions, vehicle conditions, or driving scenarios of the alert mode94 at 740, the user configured alert setting 84 are retrieved from thealert settings datastore 70 at 750. One or more of the alert patterns104-108 are set based on the user configured alert settings 84 at 760.Thereafter, the method may end at 735.

If the alert mode 94 is not an override mode at 710, and user configuredalert settings 84 do not exist for all of the one or more alertconditions, vehicle conditions or driving scenarios of the alert mode 94at 740, however user configured alert settings 84 exist for some (butnot all) of the one or more alert conditions, vehicle conditions, ordriving scenarios at 770, the user configured alert settings 84 areretrieved for the alert conditions, vehicle conditions, or drivingscenarios in which they exist at 780, and the predefined alert settings110 are retrieved for the remaining alert conditions, vehicleconditions, or driving scenarios at 790. One or more alert patterns104-108 are set based on the user configured alert settings 84 and thepredefined alert settings 110 at 800. Thereafter, the method may end at735.

If the alert mode 94 is not an override mode at 710, and user configuredalert settings 84 do not exist for all of the one or more alertconditions, vehicle conditions, or driving scenarios at 740, and in factthey do not exist for any of the one or more alert conditions, vehicleconditions, or driving scenarios at 770, the predefined alert settings110 are retrieved for the alert conditions, vehicle conditions, ordriving scenarios of the alert mode 94 at 810, and one or more alertpatterns 104-108 are set based on the predefined alert settings 110 at820. Thereafter, the method may end at 735.

With reference back to FIG. 2, when the alert mode 94 indicates multiplealert conditions, vehicle conditions, and/or driving scenarios that areassociated with multiple patterns, the pattern determination module 78coordinates the alert patterns 104-108 before being generated. Invarious embodiments, the pattern determination module 78 coordinates thealert patterns 104-108 by synchronizing a timing of the patterns,arbitrating between patterns, and/or combining patterns into a singlepattern. In various embodiments, the pattern determination module 78coordinates the alert patterns 104-108 based on whether the alertpatterns 104-108 are associated with the same alert device 50-56(FIG. 1) or with different alert devices 50-56 (FIG. 1).

For example, as shown in FIG. 7 and with continued reference to FIG. 2,the alert patterns 104-108 are evaluated at 900. If multiple alertpatterns do not exit at 910, the method may end at 915. If, however,multiple alert patterns 104-108 exist at 910, it is determined whetherany of the alert patterns 104-108 are associated with a same alertdevice 50-56 (FIG. 1) at 920. If alert patterns 104-108 are associatedwith a same alert device 50-56 (FIG. 1) at 920, the alert patterns104-108 are arbitrated or combined for each same alert device 50-56(FIG. 1) at 930 before being generated.

For example, the alert patterns 104-108 can be arbitrated based on apredefined priority scheme to determine a preferred pattern. In anotherexample, the alert patterns 104-108 can be combined or added to createunique, superimposed, and/or summative patterns without the need forarbitration. In various embodiments, the combined patterns may becombined for all or part of the alert depending on the timing of thealert.

If alert patterns 104-108 are only associated with a same alert device50-56 (FIG. 1) at 920, and are not associated with different alertdevices 50-56 (FIG. 1) at 940, the method may end at 915 (e.g., withonly combining or arbitrating patterns between a same device).

If, in addition to alert patterns 104-108 being associated with a samealert device 50-56 (FIG. 1), alert patterns 104-108 are associated withdifferent alert devices 50-56 (FIG. 1) at 940, the alert patterns104-108 between the alert devices 50-56 (FIG. 1) are furthersynchronized or arbitrated at 950 before being generated. For example,the alert devices 50-56 (FIG. 1) can be arbitrated based on a predefinedpriority scheme to determine a preferred alert device 50-56 (FIG. 1) andthe alert pattern 104-108 associated with that alert device 50-56(FIG. 1) is generated. In another example, visual, auditory, and orhaptic alert patterns 104-108 can be synchronized to issue similarpatterns (e.g., three visual alert flashes, three haptic seat pulses,and/or three beeps) without the need for arbitration. Thereafter, themethod may end at 915 (e.g., with combining or arbitrating patterns of asame device and with synchronizing or arbitrating patterns betweendifferent devices).

If, however, alert patterns 104-108 are not associated with a same alertdevice 50-56 (FIG. 1) at 920, but the alert patterns 104-108 areassociated with different alert devices 50-56 (FIG. 1) at 940, the alertpatterns 104-108 between the different alert devices 50-56 (FIG. 1) aresynchronized or arbitrated at 950, and the method may end at 915 (e.g.,with only synchronizing or arbitrating patterns between differentdevices).

With reference back to FIG. 2, the pattern determination module 78 mayfurther modify the alert patterns 104-108 from the patterns determinedfrom the user configured alert settings 84 and/or the predefined alertsettings 110 and/or modify an output of the infotainment system viainfotainment signals 116 based on interior vehicle conditions 112 and/orexterior vehicle conditions 114. The interior vehicle conditions 112 caninclude, but are not limited to, sensed or predicted acoustics of theinterior of the vehicle 10 (FIG. 1) that may impact a driver's abilityto sense the alert. The exterior vehicle conditions can include, but arenot limited to, sensed or predicted acoustics or vibrations of theexterior of the vehicle 10 (FIG. 1) that may impact the driver's abilityto sense the alert.

For example, as shown in the FIG. 8 and with continued reference to FIG.2, the vehicle conditions are received at 1000. If the vehicleconditions are interior vehicle conditions 112 at 1010, the alertpatterns 104-108 are modified based on the interior vehicle conditions112 at 1020. For example, if the evaluation of the interior vehicleconditions 112 indicate the detection of a particular song or musicbeing played on a radio of the infotainment system 56 (FIG. 1), one ormore of the haptic alert patterns 104 can be modified by increasing anintensity (e.g., a vibration intensity) based on the presence of lowfrequency content or radio volume. In another example, if the evaluationof the interior vehicle conditions 112 indicate the detection of a highvolume setting of the infotainment system 56 (FIG. 1), a low frequencyauditory alert pattern may be superimposed into the auditory content ofthe infotainment system 56 (FIG. 1) to reinforce the alert that is beingcommunicated by a haptic alert device 50 (FIG. 1).

If the vehicle conditions are interior vehicle conditions 112,alternatively or additionally, the infotainment signals 116 aregenerated based on the interior vehicle conditions 112 at 1020. Forexample, if the evaluation of the interior vehicle conditions 112indicate the detection of a high volume setting of the infotainmentsystem 56 (FIG. 1), the infotainment volume level may be reduced viainfotainment signals 116 to a level that is below the auditory alertsound level (e.g., 75 dBA), or the low frequency content (e.g., below250 Hz) may be eliminated entirely or reduced to improve the driver'sability to perceive a haptic alert via infotainment signals 116.

As can be appreciated, other interior conditions 112 may include, butare not limited to, an output of a driver distraction module, output ofa driver workload estimation module (e.g., identifying that the driveris engaged in complex driving maneuvers, identifying if the driver isreceiving an incoming call, is in an active call or is receiving urgentmaneuver indications from the navigation system), a drowsy drivermodule, or an enabled state of semi-autonomous driving systems (e.g.,cruise control, adaptive cruise control, lane keeping or lane centeringsystem). For example, if the output of the driver distraction modulesuggest a driver is in a high, prolonged state of distraction, orprolonged state of severe drowsiness, alert patterns can be changed toprovide a higher intensity alert (e.g., stronger vibration, louderalert, or brighter visual display) or an earlier alert. Similarly, ifthe driver is detected to be pressing a touch screen panel with theirfinger on an infotainment screen (which may indicate the driver's eyesare looking away from the outside traffic scene as they guide theirfinger to the desired area of the touch screen panel), alert patternscan be changed to provide a higher intensity alert (e.g., strongervibration, louder alert, or brighter visual display) or even earlieralert.

If, in addition to the vehicle conditions being interior vehicleconditions 112 at 1010, the vehicle conditions are not exterior vehicleconditions 114 at 1030, the method may end at 1050 (e.g., with modifyingpatterns 104-108 and/or generating infotainment signals 116 only basedon interior vehicle conditions 112).

If, in addition to the vehicle conditions being interior vehicleconditions 112 at 1010, the vehicle conditions are exterior vehicleconditions 114 at 1030, the alert patterns 104-108 are further modifiedbased on the exterior vehicle conditions 114 at 1040. For example, ifthe evaluation of the exterior vehicle conditions 114 indicates thedetection of vehicle vibration as indicated by a vehicle suspensionsystem (not shown), the alert patterns 104-108 are modified during roughroad conditions. In this example, the patterns 104-108 may be adjustedbased on the nature or magnitude of the vibration from the suspensionsystem. For example, if an average magnitude over a predetermined timeis determined to exceed some threshold, the alert pattern 104-108 can beadjusted to increase the vibration intensity (e.g., by a discrete value,or a value that is determined based on the magnitude). Thereafter, themethod may end at 1050 (e.g., with modifying patterns 104-108 and/orgenerating infotainment signals 116 based on interior vehicle conditions112 and with modifying patterns 104-108 based exterior vehicleconditions 114).

If, at 1010 the vehicle conditions are not interior vehicle conditions112, however, the vehicle conditions are exterior vehicle conditions 114at 1030, the alert patterns 104-108 are modified based on the exteriorvehicle conditions 114 at 1040. Thereafter, the method may end at 1050(e.g., with modifying patterns 104-108 only based exterior vehicleconditions 114).

As can be appreciated in light of the disclosure, the order of operationwithin the methods shown in the flowcharts is not limited to thesequential execution as illustrated in the figures, but may be performedin one or more varying orders as applicable and in accordance with thepresent disclosure. As can further be appreciated, one or more steps ofthe methods may be added or removed without altering the method. Invarious embodiments, the methods can be scheduled to run based onpredetermined events, and/or can run continually during operation of thevehicle.

While at least one exemplary embodiment has been presented in theforegoing detailed description, it should be appreciated that a vastnumber of variations exist. It should also be appreciated that theexemplary embodiment or exemplary embodiments are only examples, and arenot intended to limit the scope, applicability, or configuration of thedisclosure in any way. Rather, the foregoing detailed description willprovide those skilled in the art with a convenient road map forimplementing the exemplary embodiment or exemplary embodiments. Itshould be understood that various changes can be made in the functionand arrangement of elements without departing from the scope of thedisclosure as set forth in the appended claims and the legal equivalentsthereof.

What is claimed is:
 1. A method of alerting a driver of a vehicle,comprising: receiving conditions data from one or more collisionavoidance systems; determining an alert mode based on the conditionsdata; receiving a fault status indicating a fault of at least one of ahaptic alert device, a visual alert device, and an auditory alertdevice; resetting the alert mode to an override mode based on the faultstatus; and selectively generating an alert pattern for at least one ofa haptic alert device, a visual alert device, and an auditory alertdevice that does not have a fault based on the override mode of thealert mode.
 2. The method of claim 1, wherein the determining the alertmode comprises determining the alert mode to include at least one of analert condition, a driving scenario, and a vehicle condition.
 3. Themethod of claim 1, wherein the fault status indicates a fault of a firsthaptic device, and wherein the alert pattern is for a second hapticdevice.
 4. The method of claim 1, wherein the fault status indicates afault of a haptic device, and wherein the alert pattern is for at leastone of an auditory device and a visual device.
 5. The method of claim 1,wherein the fault status indicates a fault of a first auditory device,and wherein the alert pattern is for a second auditory device.
 6. Themethod of claim 1, wherein the fault status indicates a fault of anauditory device, and wherein the alert pattern is for at least one of ahaptic device and a visual device.
 7. The method of claim 1, wherein thefault status indicates a fault of a first visual device, and wherein thealert pattern is for a second visual device.
 8. The method of claim 1,wherein the fault status indicates a fault of a visual device, andwherein the alert pattern is for at least one of a haptic device and anauditory device.
 9. The method of claim 1, wherein the at least one ofthe haptic device, the auditory device, and the visual device is of aninfotainment system.
 10. The method of claim 1, wherein the receivingthe conditions data is from at least one of a line-of-sight collisionavoidance system and a non-line-of sight collision avoidance system. 11.A control system for alerting a driver of a vehicle, comprising: a firstmodule that receives conditions data from one or more collisionavoidance systems, that determines an alert mode based on the conditionsdata, that receives a fault status indicating a fault of at least one ofa haptic alert device, a visual alert device, and an auditory alertdevice, and that resets the alert mode to an override mode based on thefault status; and a second module that selectively generates an alertpattern for at least one of a haptic alert device, a visual alertdevice, and an auditory alert device that does not have a fault based onthe override mode of the alert mode.
 12. The control system of claim 11,wherein the first module determines the alert mode to include at leastone of an alert condition, a driving scenario, and a vehicle condition.13. The control system of claim 11, wherein the fault status indicates afault of a first haptic device, and wherein the alert pattern is for asecond haptic device.
 14. The control system of claim 11, wherein thefault status indicates a fault of a haptic device, and wherein the alertpattern is for at least one of an auditory device and a visual device.15. The control system of claim 11, wherein the fault status indicates afault of a first auditory device, and wherein the alert pattern is for asecond auditory device.
 16. The control system of claim 11, wherein thefault status indicates a fault of an auditory device, and wherein thealert pattern is for at least one of a haptic device and a visualdevice.
 17. The control system of claim 11, wherein the fault statusindicates a fault of a first visual device, and wherein the alertpattern is for a second visual device.
 18. The control system of claim11, wherein the fault status indicates a fault of a visual device, andwherein the alert pattern is for at least one of a haptic device and anauditory device.
 19. The control system of claim 11, wherein the atleast one of the haptic device, the auditory device, and the visualdevice is of an infotainment system.
 20. The control system of claim 11,wherein the first module receives the conditions data from at least oneof a line-of-sight collision avoidance system and a non-line-of sightcollision avoidance system.